Formal verification: resurrect fiat-crypto with formally verified assembly #430
+4,156
−0
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR resurrects the old formally verified fiat-crypto backend from fafebac
And also combines it with CryptOpt, https://github.com/0xADE1A1DE/CryptOpt, an optimizer for x86-64 field assembly.
This is to explore formally verified and correct-by-construction EVM / Ethereum with the push from the Ethereum Foundation.
Note: assembly files must be named
.S
instead of.asm
or the Nim compiler (or gcc) doesn't want to compile them properly.Performance
Unfortunately autogenerated assembly from CryptOpt is still significantly lagging behind Constantine's
AMD Ryzen 7840U (laptop 15W to 30W CPU)
23ns in Constantine vs 32ns for CryptOpt for Fp mul :/.